Skip to content

(IMPROVEMENT)(DOTNET-200) - Fallback to Config Stackify.Environment for azure instance hostname #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 21, 2025

Conversation

homiedopie
Copy link
Contributor

Overview:

  • Device name created by StackifyLIb does not match on the one created by Windows Agent if hosted in Azure AppService

Proposed Solution:

  • Sync StackifyLib and Agent’s logic to obtain the same device name if hosted in Azure AppService. Prioritize Stackify.Environment for instance name

@homiedopie homiedopie requested review from danatcofo, t-lair and kgorro June 5, 2025 22:32
@homiedopie homiedopie self-assigned this Jun 5, 2025
@homiedopie homiedopie changed the title (IMPROVEMENT)(DOTNET-199) - Fallback to Config Stackify.Environment for azure instance hostname (IMPROVEMENT)(DOTNET-199)(WIP) - Fallback to Config Stackify.Environment for azure instance hostname Jun 5, 2025
@homiedopie homiedopie changed the title (IMPROVEMENT)(DOTNET-199)(WIP) - Fallback to Config Stackify.Environment for azure instance hostname (IMPROVEMENT)(DOTNET-200) - Fallback to Config Stackify.Environment for azure instance hostname Jul 18, 2025
@homiedopie homiedopie merged commit 9afdcd1 into master Jul 21, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants